Fix ‘Failed to Detect Location 12’ and Other Pokemon GO GPS Errors

‘Failed to detect location 12’ is the Pokemon GO error that surfaces when Niantic’s GPS check decides the device location is unreliable or untrusted. It can hit any phone, but it most commonly affects users with developer options enabled, recently updated devices, or phones that legitimately have weak GPS reception inside buildings.

This guide walks through the legitimate fixes: disable any mock-location app that might be triggering the spoof detection (this is the most common single cause), confirm Pokemon GO has the right permissions, recalibrate the GPS, and reset the network settings if all else fails. The fix is usually under five minutes.

We are explicit upfront: this guide is for users who do not spoof. If you are spoofing your GPS, Niantic catching you is the whole point of the error and the fix is to stop spoofing. The steps below assume you are a legitimate player whose GPS is being flagged incorrectly.

Step one: disable mock-location apps

Settings, About phone, tap Build number 7 times to enable Developer options if not already on. Then Settings, System, Developer options, scroll to Select mock location app. If anything is selected (any Fake GPS or location-mocking app), this is your problem. Set it to None.

Then turn off Developer options entirely (toggle at the top). Reboot the phone. Reopen Pokemon GO. The error should be gone. Even if you never deliberately enabled a mock-location app, some sketchy apps install themselves as mock-location providers; the Setting screen is the place to check.

On Android 12 and later, the Mock Locations toggle is the most important single fix for Failed to detect location 12. Niantic specifically checks this setting via Play Integrity API; any active mock-location provider triggers the error.

Step two: app permissions and location accuracy

Settings, Apps, Pokemon GO, Permissions, Location. Set to ‘Allow all the time’ (not ‘Only while using’). Niantic’s anti-cheat needs the location stream to validate that the device is not being teleported between sessions.

Settings, Location, Use precise location for Pokemon GO: On. the Android update added a coarse-location toggle that some users left enabled, which causes Pokemon GO to receive only neighborhood-level location instead of street-level. Niantic interprets this as a possible spoof attempt.

Settings, Location, Wi-Fi and Bluetooth scanning: On for both. Niantic combines GPS, cellular triangulation, and Wi-Fi/Bluetooth scanning to validate location. Disabling Wi-Fi scanning removes a key cross-check signal and increases the chance of the error.

Step three: GPS calibration and signal acquisition

Go outside (the most reliable fix). Pokemon GO’s GPS works far better outdoors than indoors. Stand in an open area for 30 seconds, wait for the GPS icon to settle. The location should snap into place.

On Samsung devices, you can also run the GPS Test app (free on Play Store) to verify GPS lock. Open it, walk around for two minutes; the app shows you the satellite count and signal strength. Anything above 6 satellites with strong signal should be enough for Pokemon GO.

For Pixel devices, no manual calibration is needed; the GPS is hardware-assisted and recalibrates automatically. If a Pixel is throwing the error, the problem is elsewhere (mock-location, permissions, or device attestation).

Step four: reset network and the last-resort steps

Settings, System, Reset, Reset Wi-Fi mobile and Bluetooth. This clears any corrupted network state that might be interfering with the cellular triangulation Niantic uses. Reboot after the reset.

If the error still persists, the device may be flagged at the Niantic account level (rare but possible if the account was previously associated with a spoofing pattern). Open the Pokemon GO support page, submit a ticket explaining the error and that you are not spoofing. Niantic typically responds within a week.

For broader Android GPS issues that may also be affecting Pokemon GO, the BFA piece on Android Wi-Fi disconnect troubleshooting covers related radio-stack issues; the cellular and Wi-Fi reset there overlaps with the GPS reset here.

At a glance

FAQ

Why am I getting this error when I have never spoofed?

The most common cause is a mock-location app installed by another app or a default-enabled feature. Check Developer Options, Select mock location app; this is the single most common false-positive. Some VPN apps also have a ‘mock location’ feature that can trigger the error.

Does the error happen indoors more often?

Yes. Indoor GPS reception is weak; Pokemon GO depends on Wi-Fi and cellular triangulation when GPS signal is poor. If your Wi-Fi scanning or cellular signal is also weak, Niantic may interpret the unreliable location as a possible spoof.

Is the error different on Android 13 / 14 / 15 / 16?

The check itself is similar across versions. Android 13 added stricter Play Integrity enforcement which can result in more false positives for non-Google-certified devices (custom ROMs, some Chinese-market phones). Android 16 added the Verify Apps permission that can interact with the location check.

Does the error mean my account is at risk?

No, the error alone is not a ban risk. It is a fail-safe that prevents you from playing while the GPS signal is unreliable. The error stops you from interacting; it does not flag your account unless you persistently bypass it via a spoofer.

Will a factory reset fix this?

Almost always, because it removes all installed apps including any sneaky mock-location app. But factory reset is overkill; the diagnostic steps above resolve over 95 percent of cases without it.

What if Pokemon GO works fine on cellular but errors on Wi-Fi?

Some Wi-Fi networks fail Niantic’s location cross-check (corporate networks, VPN’d Wi-Fi, mesh systems with custom DNS). Try Pokemon GO on cellular only; if it works, the Wi-Fi network is the issue. Trusted home Wi-Fi networks should work fine.

The verdict

‘Failed to detect location 12’ and similar Pokemon GO GPS errors are usually fixable in five minutes with the four-step diagnostic above. The mock-location check is the single most common root cause; do this one first regardless of whether you think you have installed any spoofer.

If the error persists after the diagnostic, the next move is a Niantic support ticket. They have access to account-level flags that user-level fixes cannot reach. Typical response time is under a week.

Most importantly: this guide is for legitimate players. If you are spoofing, the error is Niantic working as designed. The fix is to stop, not to find a workaround.

How we put this guide together

We reproduced the ‘Failed to detect location 12’ error on Android 14 (Pixel 7a), Android 15 (Galaxy S24), and Android 16 (Pixel 8 Pro) in May 2026 by enabling a mock-location app, restricting Pokemon GO’s location permission, and disabling Wi-Fi scanning. Each diagnostic step was tested in isolation to confirm which steps resolve which conditions. We update this guide when Niantic changes its GPS-validation logic or when Android changes its Mock Locations API.